Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@apps/www/src/content/docs/components/toast/demo.ts`:
- Around line 9-11: The generated code snippets are malformed when title or
description contain quotes/backslashes; change the string interpolation in the
opts.push calls so the values are safely escaped (e.g., use
JSON.stringify(title) and JSON.stringify(description) instead of
`"${title}"`/`"${description}"`) when building the options array (the lines that
call opts.push for title and description), so the produced snippet contains a
properly escaped JS string.

In `@apps/www/src/content/docs/components/toast/index.mdx`:
- Around line 45-53: The docs import wrongly assumes a top-level named export
createToastManager from '@raystack/apsara'; fix by either updating the example
to use the actual API (import { Toast } from '@raystack/apsara' and call
Toast.createToastManager()) or, if you prefer a top-level helper, add a named
re-export: export createToastManager from the toast implementation (where
createToastManager is defined) and re-export it from the package entry so
consumers can import { createToastManager } from '@raystack/apsara'; ensure the
symbol createToastManager is exported alongside Toast to keep both usages
working.

In `@packages/raystack/components/toast/__tests__/toast.test.tsx`:
- Around line 228-250: The tests around leading icons in toast need to assert
the correct contract of ToastRoot: when leadingIcon is omitted the component
should render the default icon, and when leadingIcon is explicitly null it
should not render the leading-icon slot; update the two specs that call
toastManager.add(...) to target the leading-icon slot explicitly (e.g. via the
test id or data attribute used for the slot such as "leading-icon" or a specific
slot selector) instead of using a broad aria-hidden selector, so the first test
expects the leading-icon element to exist and the null-case test asserts that
querying the explicit leading-icon element returns null/not present.

In `@packages/raystack/components/toast/toast-root.tsx`:
- Around line 59-67: Replace truthy boolean coercion with nullish checks for
ReactNode props: change hasBoth from "!!toast.title && !!toast.description" to
"toast.title != null && toast.description != null" and update any conditional
renders that use "title && ..." or "description && ..." (including the block
around lines 95-100) to use "title != null" / "description != null" so valid
values like 0 or '' still render; similarly, where code distinguishes
leadingIcon omission vs explicit opt-out, ensure checks distinguish undefined vs
null (use "userIcon === null" to opt-out and "userIcon === undefined" to fall
back) rather than truthy checks.

---

Outside diff comments:
In `@apps/www/src/content/docs/components/toast/props.ts`:
- Around line 20-33: The ToastProviderProps interface is missing the new
toastManager prop that toast-provider.tsx now accepts; add a documented optional
toastManager property to ToastProviderProps (matching the type used/expected by
the provider in packages/raystack/components/toast/toast-provider.tsx) and
include a JSDoc comment explaining it provides a scoped manager for
adding/removing toasts so the docs surface the new scoped-manager API. Ensure
the prop name is exactly toastManager and its type aligns with the provider's
expected manager interface/constructor.

---

Nitpick comments:
In `@apps/www/src/content/docs/components/toast/demo.ts`:
- Around line 338-360: The Inner component should be moved out of HookDemo to
avoid recreating the function on every render; define Inner as a top-level
component that calls useToastManager (keeping the same JSX and Button handler)
and then have HookDemo simply return <Toast.Provider><Inner /></Toast.Provider>;
ensure Inner still uses the same identifiers (Inner, HookDemo, useToastManager,
Toast.Provider) so the demo behavior and hook usage inside the provider remain
identical while eliminating the inline-component anti-pattern.